home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19941221-19950208
/
000001_news@columbia.edu_Wed Dec 21 04:20:06 1994.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA10060
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Wed, 21 Dec 1994 15:04:56 -0500
Received: by apakabar.cc.columbia.edu id AA28387
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Wed, 21 Dec 1994 15:04:53 -0500
Path: news.columbia.edu!panix!news.mathworks.com!europa.eng.gtefsd.com!howland.reston.ans.net!cs.utexas.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: a friend having a problem
Message-Id: <1994Dec21.102006.35857@cc.usu.edu>
Date: 21 Dec 94 10:20:06 MDT
References: <pX3-kuqcZBFF075yn@primenet.com>
Organization: Utah State University
Lines: 56
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <pX3-kuqcZBFF075yn@primenet.com>, jbishop@primenet.com (Jeff Bishop) writes:
> Hello,
>
> MS-Kermit Trouble Report
>
> Date: December 21, 1994
> From: cboldt@execpc.com
>
> Description: Computer locks up solid if "set receive packet-length 2000"
> is a parameter when calling Kermit from a {Commo} macro.
>
> Harware: See msd report
> Software: MS-DOS Version 5.00
> Desqview 2.4
> kermit.exe 3.14
> 228936 11-21-94 16:06 KERMIT.EXE
> 103994 11-21-94 16:06 KERLITE.EXE
>
> Details: {Commo} is a telecommunications terminal that provides
> a way to execute external protocols. Commo ver 6.41
>
> This is done with a macro command called {EXECute }
>
> {exec kermit.exe set file type binary, set port com1, cd d:\co\dl, receive}
>
> The example command line works fine.
>
> However, if the set receive packet-length parameter is
> specified from this context, the result is a locked
> machine with the line "Bad Command or File" on line 1.
> A cold boot is required to reset.
>
> What's been tried: Varying the position of the "set receive" parm
> This results in a lock-up
>
> Attempt with kerlite.exe
> Results in a lock-up
>
> Use the "-s" parm in {Commo}'s {exec } command.
> This swaps Commo out of RAM to make more room
> for other programs. Locks-up.
>
> set receive packet-length 2000 in mskermit.ini
> This works and is in use
>
> Setting receive packet-length from Kermit>
> prompt also works, no trouble at all.
<lengthy MSD listings omitted>
---------------
Those omitted details show that program COMMO is attached to the
serial port hardware. That will be fatal if Kermit also uses the same
hardware. Thus I recommend you try without COMMO. I've never encountered
COMMO so I won't guess about it.
Also please do watch out for Smartdrive eating up cpu cycles like
crazy when it flushes to real disk.
Joe D.